The CI Fail is because of RuboCop - but it's not giving me any information - just "Hook raised unexpected error."

Great analysis but unforunately, 😢 this doesn't work on my machine. It's critical to do the gem install before the test because uninstalling pry-byebug actually fixes the original reported issue.

Running ruby test/examples/last_line.rb didn't invoke pry. If you uninstall byebug, it will invoke.

I tried adding this to my .pryrc too.

PryByebug.binding_behavior = :pry

Poop. Looks like .pryrc isn't loaded until the actual Pry repl is started. We start Byebug before we start pry, so we've either got to do the Pry.initial_session_setup ourselves, or we've got to hook later into the process. I put the setup call in the start method for now.

Ok. Yeah, that works now @stephenprater. Awesome. 👍

This is definitely required (as you know) to make pry invoke.

# ~/.pryrc
PryByebug.binding_behavior = :pry

I wonder if this would be the default if it's considered stable? @deivid-rodriguez

Guys, I'll be off until mid october or so. I'll review and consider this when I'm back.

Salud!

@deivid-rodriguez would you be able to take a look at this now? I'm running into ConradIrwin/pry-rescue#71 and this would solve the problem for me. Thanks.

@russelldavis No, sorry... I'll let you know when I get to it, but don't know when that'll be. In the mid time, you can use this branch if it works for you!